home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
AMOS PD CD
/
amospdcd.iso
/
aminet
/
amoslist0993.lzh
/
AMOSLIST2
/
000074_amos-request@svcs1.digex.net_Fri Sep 3 01:16:48 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-09-03
|
3KB
Received: from nextsun.INS.CWRU.Edu by access.digex.net with SMTP id AA11896
(5.65c/IDA-1.4.4 for <mcox@access.digex.com>); Fri, 3 Sep 1993 01:16:46 -0400
Received: from svcs1.digex.net by nextsun.INS.CWRU.Edu with SMTP (5.65b+ida+/CWRU-1.5.2-freenet-gw)
id AA09808; Fri, 3 Sep 93 01:15:18 -0400 (from amos-request@svcs1.digex.net for mcox@access.digex.com)
Received: by svcs1.digex.net id AA28335
(5.65c/IDA-1.4.4 for amos-list-out); Fri, 3 Sep 1993 01:04:05 -0400
Received: from access.digex.net by svcs1.digex.net with SMTP id AA28331
(5.65c/IDA-1.4.4 for <amos-list@svcs1.digex.net>); Fri, 3 Sep 1993 01:04:03 -0400
Received: from mailgate.ericsson.se by access.digex.net with SMTP id AA07457
(5.65c/IDA-1.4.4 for <amos-list@access.digex.net>); Fri, 3 Sep 1993 01:03:59 -0400
Received: from eua.ericsson.se by mailgate.ericsson.se (4.1/SMI-4.1-MAILGATE1.14)
id AA09211; Fri, 3 Sep 93 07:03:51 +0200
Received: from ms.eua.ericsson.se by eua.ericsson.se (4.1/EUA-2.1)
id AA25301; Fri, 3 Sep 93 07:03:49 +0200
Received: from euax1i6c18.eua.ericsson.se by ms.eua.ericsson.se (4.1/MS-2.1)
id AA11367; Fri, 3 Sep 93 07:03:48 +0200
From: Per.Lundholm@eua.ericsson.se (Per Lundholm)
Received: by euax1i6c18.eua.ericsson.se (4.1/client-1.3)
id AA00498; Fri, 3 Sep 93 07:03:48 +0200
Date: Fri, 3 Sep 93 07:03:48 +0200
Message-Id: <9309030503.AA00498@euax1i6c18.eua.ericsson.se>
To: amos-list@access.digex.net, czar1@manta.nosc.mil
Subject: Re: General
Status: O
> My question is in reference to testing to see if the current computer
> has a battery backed clock or not. Is there a way to automatically do this?
> (This helps automatically configure current week.)
Is this really what you want? Surely it shouldn't matter whether there is
a (functioning) battery or not? You'd probably be more intersted if the
current system date reflects reality. After all, even if there is no battery
backup, the usr may have typed in the correct date.
^^^
(Sorry, running UNIX :))
Given that the ASS-U-ME-d* above is correct, you may either store current
date in a file, when the prog is run the next time you should see if the
date is reasonable. Or, you could ask the user if the date is correct.
Suggestions that may both be used.
> I have spent 3 years developing this, and have gone through 3 complete
> rewrites!!! Currently my routine that handles the predictions is running
> about 80% accurate vesrses the win-loss ratio. (Actual points and against
> the line is abit lower.)
80% is more than 50%, so your program is better than chance. How does it
compare in other aspects? I guess that NFL is about American football and
there is actully a possibility to bet on that here in Sweden, but only on
the Super Bowl (as far as I know).
> I am almost to the point that I would appreciate anyone that would like
> to aid me in alfa & beta testing the software. Eventually I will most
> likley release a "hampered" version as shareware, and with registration I
> will mail them the fully fuctional version. (ie: modify schedules;
> multi-years; maybe future expansion to enable any team name and stats to be
> used - ???)
The task of your life ;).
/Per
*-footnote:
Whenever we assume it makes an ASS of U and ME. Good programming rule.
The same.